Server side authentication

ABSTRACT

A server may perform server side authentication of a user device. The user device may generate a first authentication string by performing a hash function on a username, a password, and a first salt. The first authentication string may be registered with the server for subsequent login attempts. At login, the user device generates the first authentication string and transmits the first authentication string to the server. When the authentication strings match, the user device is authenticated. The user device may also update the first authentication string. The server may provide the first salt and a second salt to the user device. The user device may generate a first authentication string and a second authentication string from the first salt and the second salt, respectively. When the first authentication strings match, the server may update the user device&#39;s authentication string by replacing it with the second authentication string.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of co-pending application U.S.application Ser. No. 16/686,431, filed on Nov. 18, 2019 and entitled“Server Side Authentication,” the entirety of which is herebyincorporated in its entirety by reference.

FIELD OF USE

Aspects of the disclosure relate generally to authentication and morespecifically to server-side authentication.

BACKGROUND

Server-based authentication schemes traditionally require a user toregister a password during account creation. The password is stored in apassword file or database as a comparison for future log-in attempts.Some systems may store the password as plaintext, while other systemsmay provide some layer of security by obfuscating the stored password.During a log-in attempt, the user may transmit the password from theuser device to the server. The server may receive the passwordassociated with the log-in attempt and compare the received passwordwith the previously registered password. When the passwords match, theuser may be authenticated and granted access. While this affords onetechnique for authenticating users, it suffers from severalvulnerabilities. For example, the user's password may be intercepted bya malicious actor in-transit between the user device and the server.Additionally, the server may be breached in a way that provides themalicious actor access to the user's username and password. Becausepeople are bad at remembering passwords, people oftentimes reuse thesame username and password on multiple systems. Thus, a single breach ofthe user's username and password may provide the malicious actor withaccess to several, if not all, of the user's accounts.

Aspects described herein may address these and other problems, andgenerally improve the security, efficiency, and speed with whichserver-side authentication occurs.

SUMMARY

The following presents a simplified summary of various aspects describedherein. This summary is not an extensive overview, and is not intendedto identify key or critical elements or to delineate the scope of theclaims. The following summary merely presents some concepts in asimplified form as an introductory prelude to the more detaileddescription provided below. Corresponding apparatus, systems, andcomputer-readable media are also within the scope of the disclosure.

Example methods and systems as described herein may include server sideauthentication. As part of a registration process, a server may generatea salt and transmit the salt to the user device. In response toreceiving the salt, the user device may derive an authentication stringusing the salt, a username, and a password. The authentication stringmay be transmitted to the server, along with the username, to registerthe user. During subsequent log-in attempts, the server may retrieve thesalt from memory and transmit the salt to the user device. The userdevice may generate an authentication string using the received salt,their username, and their password. The generated authentication stringmay be transmitted to the server for authentication purposes. The servermay receive the generated authentication string and compare thegenerated authentication string to the previously-registeredauthentication string. When the authentication strings match, the usermay be authenticated and granted access.

Example methods and systems may also describe a rehydration technique,wherein users may update their authentication information. In responseto request to update authentication information, the server may retrievea first salt from memory and generate a second salt. The first salt andthe second salt may then be sent (e.g., transmitted) to the user device.The user device may derive a first authentication string using the firstsalt, a username, and a password of the user. Additionally, the userdevice may generate a second authentication string using the secondsalt, the username, and the password. The username, the firstauthentication string, and the second authentication string may betransmitted to the server. The server may compare the firstauthentication string to a previously-registered authentication string.When the authentication strings match, the server may update the user'sauthentication information including, for example, replacing the firstsalt with the second salt and replacing the previously-registeredauthentication string with the second authentication string

These features, along with many others, are discussed in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is described by way of example and not limited inthe accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIG. 1 shows an example of a control processing system in which one ormore aspects described herein may be implemented;

FIG. 2 shows an example computing device in accordance with one or moreaspects described herein;

FIG. 3 shows a flow chart of a process for registering a new account ata user device according to one or more aspects of the disclosure;

FIG. 4 shows a flow chart of a process for registering a new account ata server according to one or more aspects of the disclosure;

FIG. 5 shows a flow chart of a system for creating a new accountaccording to one or more aspects of the disclosure;

FIG. 6 shows an example of stored user account information according toone or more aspects of the disclosure;

FIG. 7 shows a flow chart of a process for logging in according to oneor more aspects of the disclosure;

FIG. 8 shows a flow chart of a process for verifying a login requestaccording to one or more aspects of the disclosure;

FIG. 9 shows an example of a system for logging in according to one ormore aspects of the disclosure;

FIG. 10 shows a flow chart of a process for updating an authenticationstring at a user device according to one or more aspects of thedisclosure;

FIG. 11 shows a flow chart of a process for updating an authenticationstring at a server according to one or more aspects of the disclosure;and

FIG. 12 shows an example of a system for updating an authenticationstring according to one or more aspects of the disclosure.

DETAILED DESCRIPTION

In the following description of the various embodiments, reference ismade to the accompanying drawings, which form a part hereof, and inwhich is shown by way of illustration various embodiments in whichaspects of the disclosure may be practiced. It is to be understood thatother embodiments may be utilized and structural and functionalmodifications may be made without departing from the scope of thepresent disclosure. Aspects of the disclosure are capable of otherembodiments and of being practiced or being carried out in various ways.In addition, it is to be understood that the phraseology and terminologyused herein are for the purpose of description and should not beregarded as limiting. Rather, the phrases and terms used herein are tobe given their broadest interpretation and meaning.

By way of introduction, aspects discussed herein may relate to methods,systems, and techniques for server-side authentication. Instead oftransmitting a password to a server for authentication purposes, a userdevice may transmit an authentication string that is derived from theuser's password. The user's password may never leave the user's device.If the server is compromised and/or the authentication stringintercepted in-transit, the authentication string may be compromised,while the user's password remains secure. This may provide security touser accounts that use the same password for authentication.

Example methods and systems as described herein may include server-sideauthentication. As part of a registration process, a server may generatea salt and transmit the salt to the user device. In some examples, theserver may store the salt. In response to receiving the salt, the userdevice may derive an authentication string using the salt, a username,and a password. The authentication string may be transmitted to theserver, along with the username, to register the user.

During subsequent log-in attempts, the server may retrieve the salt frommemory and transmit the salt to the user device as part of the log-inprocess. The user device may generate an authentication string using thereceived salt, their username, and their password. The generatedauthentication string may be transmitted to the server forauthentication purposes. The server may receive the generatedauthentication string and compare the generated authentication string tothe previously-registered authentication string. When the authenticationstrings match, the user may be authenticated and granted access.

From time-to-time, a rehydration process may be performed that allowsthe user to update their authentication information, including theirregistered authentication string. The update may occur based on, or inresponse to, a breach detected at the server. Additionally, oralternatively, the user may prompt the update, for example, by selectingan update (e.g., change) password option. The server may retrieve afirst salt from memory and generate a second salt. The first salt andthe second salt may then be sent (e.g., transmitted) to the user device.In response to receiving the first salt and the second salt, the userdevice may derive a first authentication string and a secondauthentication string. The first authentication string may be generatedfrom the first salt, a username, and a password of the user. Similarly,the second authentication string may be generated from the second salt,the username, and the password. The user device may then send (e.g.,transmit) the username, the first authentication string, and the secondauthentication string to the server. The server may receive theusername, the first authentication string, and the second authenticationstring and retrieve a previously-registered authentication string usingthe received username. The server may compare the first authenticationstring and the previously-registered authentication string. When theauthentication strings do not match, the authentication informationupdate may be denied. However, when the authentication strings match,the server may update the user's authentication information. Updatingthe user's authentication information may include replacing the firstsalt with the second salt and replacing the previously-registeredauthentication string with the second authentication string

By using the techniques described herein, a user's password may besecured if the authentication string is intercepted in-transit and/orthe server is breached since the password never leaves the user'sdevice. A malicious actor may merely obtain a derivative of the user'spassword, thereby securing the user's account and any other additionalaccounts that use the same username and password.

Turning to FIG. 1 , a system 100 is shown that includes a first userdevice 110, a second user device 120, and a server 130, connected to afirst database 140, interconnected via network 150.

First user device 110 may be a mobile device, such as a cellular phone,a mobile phone, a smart phone, a tablet, or a laptop. First user device110 may provide a first user with access to various applications andservices. For example, first user device 110 may provide the first userwith access to the Internet. Additionally, first user device 110 mayprovide the first user with one or more applications (“apps”) locatedthereon. The one or more applications may provide the first user with aplurality of tools and access to a variety of services. In someembodiments, the one or more applications may require a user to enter ausername and password before accessing the application. In this regard,the one or more application may be any suitable application obtainedfrom a website, an online retail store or a digital distributionservice, such as iTunes® or Google Play®, that that may perform thelogin and/or authentication techniques described herein.

Second user device 120 may be a computing device configured to allow auser to execute software for a variety of purposes. Second user device120 may belong to the first user that accesses first user device 110,or, alternatively, second user device 120 may belong to a second user,different from the first user. Second user device 120 may be a desktopcomputer, laptop computer, or, alternatively, a virtual computer. Thesoftware of second user device 120 may include one or more web browsersthat provide access to websites on the Internet. In some embodiments,second user device 120 may include one or more applications. The one ormore application may be any suitable application obtained from awebsite, an online retail store or a digital distribution service thatmay perform the login and/or authentication techniques described herein.

Server 130 may be any server capable of executing server-sideapplication 132. Additionally, server 130 may be communicatively coupledto first database 140. In this regard, server 130 may be a stand-aloneserver, a corporate server, or a server located in a server farm orcloud-computer environment. According to some examples, server 130 maybe a virtual server hosted on hardware capable of supporting a pluralityof virtual servers.

First database 140 may be configured to store information on behalf ofserver 130 and/or server-side application 132. According to someembodiments, first database 140 may be a database or table configured toprovide directory services, for example, using Lightweight DirectoryAccess Protocol (LDAP), Active Directory, or an equivalent directoryservice. For instance, first database 140 may include a corporatedirectory that comprises employees' information, such as the employees'first and last names, usernames, email addresses, phone numbers,department information, authentication information (e.g., passwords,authentication strings), etc. In some embodiments, first database 140may be encrypted to protect the information contained therein. Firstdatabase 140 may include, but are not limited to relational databases,hierarchical databases, distributed databases, in-memory databases, flatfile databases, XML databases, NoSQL databases, graph databases, and/ora combination thereof. In some examples, database 140 and server 130 maybe located on the same physical computing device.

First network 150 may include any type of network. In this regard, firstnetwork 150 may include the Internet, a local area network (LAN), a widearea network (WAN), a wireless telecommunications network, and/or anyother communication network or combination thereof. It will beappreciated that the network connections shown are illustrative and anymeans of establishing a communications link between the computers may beused. The existence of any of various network protocols such as TCP/IP,Ethernet, FTP, HTTP and the like, and of various wireless communicationtechnologies such as GSM, CDMA, WiFi, and LTE, is presumed, and thevarious computing devices described herein may be configured tocommunicate using any of these network protocols or technologies. Thedata transferred to and from various computing devices in system 100 mayinclude secure and sensitive data, such as login information (e.g.,username and password, username and authentication string), confidentialdocuments, customer personally identifiable information, and accountdata. Therefore, it may be desirable to protect transmissions of suchdata using secure network protocols and encryption, and/or to protectthe integrity of the data when stored on the various computing devices.For example, a file-based integration scheme or a service-basedintegration scheme may be utilized for transmitting data between thevarious computing devices. Data may be transmitted using various networkcommunication protocols. Secure data transmission protocols and/orencryption may be used in file transfers to protect the integrity of thedata, for example, File Transfer Protocol (FTP), Secure File TransferProtocol (SFTP), and/or Pretty Good Privacy (PGP) encryption. In manyembodiments, one or more web services may be implemented within thevarious computing devices. Web services may be accessed by authorizedexternal devices and users to support input, extraction, andmanipulation of data between the various computing devices in the system100. Web services built to support a personalized display system may becross-domain and/or cross-platform, and may be built for enterprise use.Data may be transmitted using the Secure Sockets Layer (SSL) orTransport Layer Security (TLS) protocol to provide secure connectionsbetween the computing devices. Web services may be implemented using theWS-Security standard, providing for secure SOAP messages using XMLencryption. Specialized hardware may be used to provide secure webservices. For example, secure network appliances may include built-infeatures such as hardware-accelerated SSL and HTTPS, WS-Security, and/orfirewalls. Such specialized hardware may be installed and configured insystem 100 in front of one or more computing devices such that anyexternal devices may communicate directly with the specialized hardware.

Any of the devices and systems described herein may be implemented, inwhole or in part, using one or more computing systems described withrespect to FIG. 2 . Turning to FIG. 2 , a computing device 200 isdescribed. The computing device 200 may include a processor 203 forcontrolling overall operation of the computing device 200 and itsassociated components, including RAM 205, ROM 207, input/output device209, accelerometer 211, global-position system antenna 213, memory 215,and/or communication interface 223. A data bus may interconnectprocessor(s) 203, RAM 205, ROM 207, memory 215, I/O device 209,accelerometer 211, global-position system receiver/antenna 213, memory215, and/or communication interface 223. In some embodiments, computingdevice 200 may represent, be incorporated in, and/or include variousdevices such as a desktop computer, a computer server, a mobile device,such as a laptop computer, a tablet computer, a smart phone, any othertypes of mobile computing devices, and the like, and/or any other typeof data processing device.

Input/output (I/O) device 209 may include a microphone, keypad, touchscreen, and/or stylus through which a user of the computing device 200may provide input, and may also include one or more of a speaker forproviding audio output and a video display device for providing textual,audiovisual, and/or graphical output. In some embodiments, I/O device209 may include an image capture device, such as a camera. Software maybe stored within memory 215 to provide instructions to processor 203allowing computing device 200 to perform various actions. For example,memory 215 may store software used by the computing device 200, such asan operating system 217, application programs 219, and/or an associatedinternal database 221. The various hardware memory units in memory 215may include volatile and nonvolatile, removable and non-removable mediaimplemented in any method or technology for storage of information suchas computer-readable instructions, data structures, program modules, orother data. Memory 215 may include one or more physical persistentmemory devices and/or one or more non-persistent memory devices. Memory215 may include, but is not limited to, random access memory (RAM) 205,read only memory (ROM) 207, electronically erasable programmable readonly memory (EEPROM), flash memory or other memory technology, opticaldisk storage, magnetic cassettes, magnetic tape, magnetic disk storageor other magnetic storage devices, or any other medium that may be usedto store the desired information and that may be accessed by processor203.

Accelerometer 211 may be a sensor configured to measure acceleratingforces of computing device 200. Accelerometer 211 may be anelectromechanical device. Accelerometer may be used to measure thetilting motion and/or orientation computing device 200, movement ofcomputing device 200, and/or vibrations of computing device 200. Theacceleration forces may be transmitted to the processor to process theacceleration forces and determine the state of computing device 200.

GPS receiver/antenna 213 may be configured to receive one or moresignals from one or more global positioning satellites to determine ageographic location of computing device 200. The geographic locationprovided by GPS receiver/antenna 213 may be used for navigation,tracking, and positioning applications.

Communication interface 223 may include one or more transceivers,digital signal processors, and/or additional circuitry and software forcommunicating via any network, wired or wireless, using any protocol asdescribed herein.

Processor 203 may include a single central processing unit (CPU), whichmay be a single-core or multi-core processor, or may include multipleCPUs. Processor(s) 203 and associated components may allow the computingdevice 200 to execute a series of computer-readable instructions toperform some or all of the processes described herein. Although notshown in FIG. 2 , various elements within memory 215 or other componentsin computing device 200, may include one or more caches, for example,CPU caches used by the processor 203, page caches used by the operatingsystem 217, disk caches of a hard drive, and/or database caches used tocache content from database 221. For embodiments including a CPU cache,the CPU cache may be used by one or more processors 203 to reduce memorylatency and access time. A processor 203 may retrieve data from or writedata to the CPU cache rather than reading/writing to memory 215, whichmay improve the speed of these operations. In some examples, a databasecache may be created in which certain data from a database 221 is cachedin a separate smaller database in a memory separate from the database,such as in RAM 205 or on a separate computing device. For instance, in amulti-tiered application, a database cache on an application server mayreduce data retrieval and data manipulation time by not needing tocommunicate over a network with a back-end database server. These typesof caches and others may be included in various embodiments, and mayprovide potential advantages in certain implementations of devices,systems, and methods described herein, such as faster response times andless dependence on network conditions when transmitting and receivingdata.

Although various components of computing device 200 are describedseparately, functionality of the various components may be combinedand/or performed by a single component and/or multiple computing devicesin communication without departing from the invention.

As part of a new account creation and/or new registration process, auser may generate and/or register baseline authentication information(e.g. username, password, authentication string, etc.) that may serve asa comparison point for subsequent login attempts. FIG. 3 shows a flowchart of a process for registering a new account at a user deviceaccording to one or more aspects of the disclosure. Some or all of thesteps of process 300 may be performed using one or more computingdevices as described herein.

In step 310, a user device (e.g., an application executing on the userdevice) may register a username. The username may be entered as part ofa new account creation, for example, based on downloading and installinga new application. Additionally, or alternatively, the username may beentered via a webpage as part of a new account creation process. Inthese examples, the user device may transmit the username to a server toverify that the username is available. The user device may transmit theusername to the server via a secure communication channel, such as achannel secured using SSL, TLS, or an equivalent thereof. When theserver indicates that the username is not available, the user device maybe notified and the user may be prompted to select a different username.This process may continue, for example, until the username selects aunique username. In some embodiments, a username may be assigned as partof the registration process, for example, by an administrator.

In step 320, the user device (e.g., an application executing on the userdevice) may receive confirmation of the username and a salt. Theconfirmation of the username and the salt may be received from theserver via a secure communication channel (e.g., SSL, TLS). The userdevice (e.g., the application executing on the user device) may promptthe user to enter a password, for example, based on or in response toreceiving the confirmation and the salt. In step 330, the user device(e.g., the application executing on the user device) may generate anauthentication string. The authentication string may be a derivative(e.g., hashed representation) of the user's password. The authenticationstring may be derived by performing a one-way transformation (e.g., MD5,SHA128, SHA256, SHA512, PBKDF2, BCrypt, SCrypt, etc.) on the username,password, and the salt. In some instances, the username and/or passwordmay be padded before being hashed. As a result of the one-waytransformation (e.g., hash function), the authentication string may be afixed quantity (e.g., number) of bits (e.g., 64, 128, 256, 512, etc.)that has a high degree of entropy (e.g., randomness).

In step 340, the user device (e.g., the application executing on theuser device) may transmit the authentication string to the server. Insome embodiments, the username may be transmitted with theauthentication string. The username and/or authentication string may betransmitted via a secure communication channel (e.g., SSL, TLS). Byderiving an authentication string from the user's password, the user'spassword may never leave the user device. This may prevent the user'spassword from being intercepted in-transit between the user device andthe server. Additionally, the user may not have to update one or morepasswords, for example, based on a breach at the server since the serveronly has a derivative of the user's password.

In step 350, the user device (e.g., the application executing on theuser device) may complete the registration process. Completing theregistration process may include receiving a notification from theserver that the registration has been finalized. Additionally, oralternatively, completing the registration process may include obtaininguser information (e.g., name, address, phone number, email address,etc.) from the user to finalize their account information.

During a new account creation and/or new registration process, a servermay verify information provided by the user device and create an entryfor the new user account. FIG. 4 shows a flow chart of a process forregistering a new account at a server according to one or more aspectsof the disclosure. Some or all of the steps of process 400 may beperformed using one or more computing devices as described herein.

In step 410, a server may receive an indication of a new accountcreation/registration. The indication may be received over a securecommunication channel (e.g., SSL, TLS, etc.). Additionally, theindication may include a username. As noted above, the server may verifywhether the username is available. For example, the server may query adatabase and/or password file (e.g., /etc/passwd, % SystemRoot%/system32/config/SAM) using the username to determine whether theusername is available. When the username is available, the server maygenerate an entry for the user account in the database and/or passwordfile. Additionally, the server may generate a salt (e.g., initializationvector, etc.) in step 420. The salt may be a pseudorandom characterstring generated by a pseudorandom number generator. Additionally, oralternatively, the pseudorandom character string may be derived from afile (e.g., /dev/urandom, /dev/arandom, etc.) that collectsenvironmental noise from the server (e.g., device drivers, etc.).

In step 430, the server may transmit a confirmation of the username andthe salt to the user device. The confirmation and the salt may betransmitted over a secure communication channel (e.g., SSL, TLS, etc.).In step 440, the server may receive the authentication string. Theauthentication string may be received over a secure communicationchannel. In some examples, the server may receive thepreviously-registered username with the authentication string. In step450, the server may store the username and authentication string. Theusername and authentication string may be stored in a database, such asdatabase 140. In particular, the server may store the username andauthentication string in the previously generated entry in the databaseand/or password file.

In step 460, the server may complete the registration process. This mayinclude finalizing the user account entry in the database and/orpassword file. Finalizing the user account entry may include enteringand saving, the user's name, address, phone number, email address, etc.Additionally, or alternatively, the salt may be stored in the databaseand/or password file. In some examples, the server may send (e.g.,transmit) a notification to the user device that the registrationprocess has completed.

Turning to FIG. 5 , an example of a system for creating a new accountaccording to one or more aspects of the disclosure is shown. System 500includes first user device 110, server 130, and database 140. At step510, first user device 110 may transmit a new account creation requestto server 130. As noted above the new account creation request mayinclude a username. The server 130 may verify the username is available.When the username is available, server 130 may generate a salt. In step520, the server 130 may transmit confirmation of the username and thesalt to the first user device. The first user device 110 may receive theconfirmation and the salt. In step 530, the first user device 110 maygenerate the authentication string. As discussed above, the first userdevice 110 may generate the authentication string by performing aone-way transformation (e.g., hash function) on the username, apassword, and the salt. In step 540, the first user device 110 maytransmit the username and the authentication string to the server. Instep 550, the server 130 may store the username, authentication string,and salt in database 140.

As noted above, the server may create an entry in a database and/orpassword file each time a new account is generated. FIG. 6 shows anexample of stored user account information according to one or moreaspects of the disclosure.

The stored user account information may be stored in a database, such asdatabase 140 described above. Additionally, or alternatively, the useraccount information may be stored in a password file. The user accountinformation may comprise a username column 610, a salt column 620, andan authentication string 630. The username column 610 may compriseusernames, or other aliases, for registered accounts. The salt column620 may comprise a pseudorandom number generated by the server (e.g.,server-side application executing on server 130) and transmitted to theuser device to derive the authentication string. The authenticationstring column 630 may comprise the authentication provided by the userdevice during the account creation and/or registration process. Whileusername column 610, salt column 620, and authentication string 630 areillustrated in FIG. 6 , it will be appreciated that the user accountinformation may include additional information. For example, the useraccount information may include the user's actual name (e.g. first name,last name), a user identifier number, a group identifier number, a gecosfield, and the like. The user identifier number may be an employeeidentification number or any equivalent thereof that the system mayconfigured to identify the user to the system. The group identifiernumber may identify a user group that the user belongs to, such as theuser's workgroup (e.g., sales, marketing, legal, etc.). The groupidentifier number may also be configured to identify the user'spermissions (e.g. read access, write access). The gecos field mayinclude general information about the user, such as the user's fullname, office phone number, home telephone number, and/or additionalcontact information (e.g., cell phone, email, supervisor, etc.).

Once the user has completed registration, the user may use theinformation provided during the registration process to performsubsequent logins. FIG. 7 shows a flowchart of a process for logging inaccording to one or more aspects of the disclosure. Some or all of thesteps of process 700 may be performed using one or more computingdevices as described above.

In step 710, a user device (e.g., an application executing on the userdevice) may send (e.g., transmit) a login request to a server. The loginrequest may comprise a username. In some examples, the login request maybe transmitted over a secure communication channel, such as one securedby SSL, TLS, or the like. In step 720, the user device may receive asalt. The salt may be received from the server over the securecommunication channel. The salt may be received, for example, based onor in response to transmitting the login request. In some examples, thesalt may be stored in a secure memory of the user device. Accordingly,the salt may be retrieved from the secure memory during a login attempt.In these examples, step 720 may be skipped.

In step 730, the user device (e.g., the application executing on theuser device) may generate the authentication string. The authenticationstring may be generated by performing a one-way transformation (e.g.,hash function) on the username, the password, and the salt. In someexamples, the username and/or the password may be padded prior to beinghashed. The padding information may be a random string of dataconfigured to extend the username and/or password to a fixed length. Instep 740, the user device may send (e.g., transmit) the username and theauthentication string to the server. As noted above, the username andthe authentication string may be transmitted over a secure communicationchannel. In step 750, the user device (e.g., the application executingon the user device) may receive a notification from the server. When thelogin request is successful, the user device may receive indication thatthe login request was successful. The user device may be provided accessto one or more services provided by the server and/or a server-sideapplication. When the login request is not successful, the user devicemay be notified of such. The user device may be provided an opportunityto login again. In some instances, the user device may have to wait acertain period of time before attempting another login request.

In response to receiving a login request, the server may provide theuser device with a salt and verify the login request. FIG. 8 shows aflow chart of a process for verifying a login request according to oneor more aspects of the disclosure. Some or all of the steps of process800 may be performed using one or more computing devices as describedherein.

In step 810, a server may receive a login request from a user device. Asnoted above, the user device may comprise a username. In step 820, theserver may retrieve a salt. Retrieving the salt may comprise querying adatabase and/or password file using the username received in the loginrequest. The query may return the salt associated with the username. Instep 830, the server may transmit the salt to the user device. The saltmay be transmitted over a secure communication channel (e.g., SSL, TLS,etc.). In step 840, the server may receive the username and anauthentication string over a secure communication channel from the userdevice. In step 850, the server may retrieve a previously-registeredauthentication from a database and/or a password file. Again, the servermay use the username received with the authentication string to querythe database and/or the password file. In response to the query, theserver may receive the previously-registered authentication string fromthe database and/or the password file. In step 860, the server maycompare the received username and the received authentication string tothe previously-registered username and the previously-registeredusername. In some instances, the server may compare the receivedauthentication string and the previously-registered username. When thereceived authentication string and the previously-registered username donot match, the server may deny access to the user device in step 870.However, when the received authentication string and thepreviously-registered username match, the server provides access to theuser device in step 880.

Turning to FIG. 9 , an example of a system for logging in according toone or more aspects of the disclosure is shown. System 900 includesfirst user device 110, server 130, and database 140. At step 905, theuser device 110 may transmit a login request to server 130. The loginrequest may include a username and be transmitted via a securecommunication channel. The server 130 may transmit a request for a saltto database 140 in step 910. As noted above, the request for the saltmay be a query. The query may include the username received in the loginrequest. In some examples, the request for the salt may be transmittedover a secure communication channel. In other examples, the database 140may be co-located with server 130. In step 915, the database 140 mayprovide the salt to server 130. In step 920, the server 130 may transmitthe salt to the user device 110. In step 925, the user device 110 maygenerate an authentication string using the techniques described herein.In step 930, the user device 110 may send (e.g., transmit) the usernameand the generated authentication string to the server 130. In step 935,the server 130 may request a previously-registered authentication stringfrom database 140. The request may be a database may be a query thatincludes the received username. In response to the request, the database140 may send (e.g., transmit) the previously-registered authenticationstring to the server 130 in step 940. In step 945, the server 130 mayauthenticate the login request. Authenticating the login request maycomprise comparing the received authentication string and thepreviously-registered authentication string. When the authenticationstrings do not match, the login request may be denied. However, when theauthentication strings match, the login request may be verified and theuser device may be provided access in step 950.

It will be appreciated that the above login techniques may be used aloneor in combination with other authentication techniques. For example, theauthentication string discussed above may be used as part of amulti-factor authentication process. For example, a user may providetheir username and authentication string, as well as a biometricidentifier (e.g., facial recognition, fingerprint, voiceprint, retinascan, iris scan, etc.). In these examples, the user may register one ofmore biometric identifiers. During subsequent login attempts, the usermay provide their username, authentication string, and biometricidentifier to gain access. Additionally, or alternatively, theauthentication processes discussed above may be used in conjunction witha token that generates a one-time code (e.g. password, passphrase,etc.). Accordingly, the user may provide their username, authenticationstring, and a one-time code during login attempts.

Furthermore, by employing the login techniques described herein, theuser's password may remain secure on the user device. This reduces thelikelihood of a malicious actor obtaining the user's password while thepassword is in-transit. Additionally, using a derivative of a passwordfor authentication purposes secures the user's password in case of abreach at the server. This may ensure that other accounts that have thesame username and password would not be compromised in the event of abreach of the server. Accordingly, the user may not have to takecorrective action (e.g., update their passwords on other accounts) inresponse to a breach that occurs at a third-party (e.g., server),thereby improving the overall user experience.

From time-to-time, a user device may be required to perform rehydrationand/or update their authentication information and, in particular, itsauthentication string. This update may be initiated by the user device,for example, in response to a user request to update their password.Alternatively, the update may be initiated by the server, for example,based on or in response to detecting a data breach. FIG. 10 shows aflowchart of a process for updating an authentication string at a userdevice according to one or more aspects of the disclosure. Some or allof the steps of process 1000 may be performed using one or morecomputing devices as described herein.

In step 1010, the user device (e.g., an application executing on theuser device) may receive a first salt and a second salt. The first saltand the second salt may be received over a secure communication channel(e.g., SSL, TLS, etc.). In some examples, the first salt and the secondsalt may be received in a single communication. Alternatively, the firstsalt and the second salt may be received in separate communications. Instep 1020, the user device may generate a first authentication string.The first authentication string may be generated by performing a one-waytransformation (e.g., hash function) on a username, a password, and thefirst salt. As noted above, the username and/or the password may bepadded prior to being hashed. In step 1030, the user device may generatea second authentication string. The second authentication string may begenerated by performing a one-way transformation (e.g., hash function)on the username, the password, and the second salt. As noted above, theusername and/or the password may be padded prior to being hashed. Instep 1040, the user device may transmit the username, the firstauthentication string, and the second authentication string to theserver. The username, the first authentication string, and the secondauthentication may be transmitted to the server, via a securecommunication channel, in at least one communication. In step 1050, theuser device may receive notification from the server that the user'sauthentication information has been updated.

Turning to FIG. 11 , a flow chart of a process of updating anauthentication string at a server is shown. Some or all of the steps ofprocess 1100 may be performed using one or more computing devicesdescribed herein.

In step 1105, the server may detect an update event. The update eventmay be a request from a user to update authentication information.Additionally, or alternatively, the update event may be a breachdetected at the server. At step 1110, the server may retrieve the firstsalt. As noted above, the first salt may be retrieved from a databaseand/or password file via a query. In step 1115, the server may generatea second salt. The second salt may be generated using the techniquesdescribed above. For example, the second salt may be a pseudorandomcharacter string generated by a pseudorandom number generator. In step1120, the server may transmit the first salt and the second salt to theuser device. In some examples, the server may transmit the first saltand the second salt in one or more communications via a securecommunication channel. In response to transmitting the first salt andthe second salt, the server may receive a username, a firstauthentication string, and a second authentication string from the userdevice in step 1125. In step 1130, the server may determine whether thefirst authentication string matches a stored (e.g.,previously-registered) authentication string. When the authenticationstrings do not match, the server may deny the update in step 1135. Instep 1140, the server may notify the user device was denied. In someexamples, the update process may be repeated until the authenticationstring is updated. When the authentication strings match, the serer mayreplace the first authentication string with the second authenticationstring in step 1145. Replacing the first authentication string maycomprise overwriting the first authentication string with the secondauthentication string in a database and/or password file. Additionally,the first salt may be replaced (e.g., overwritten) by the second salt inthe database and/or password file. In step 1150, the server may notifythe user device that the authentication information has beensuccessfully updated. The notification may be a communication, such asan acknowledgement, transmitted to the user device. Additionally, oralternatively, the notification may be a push notification from theserver to the user device.

Turning to FIG. 12 , a system 1200 for updating authenticationinformation is shown. The system 1200 includes first user device 110,server 130, and database 140. In response to detecting an update event(e.g., a breach), server 130 may transmit a request for a first salt todatabase 140 in step 1205. In step 1210, the server 130 may receive thefirst salt from the database 140. In step 1215, the server 130 maygenerate a second salt, for example, based on or in response toreceiving the first salt from database 140. In step 1220, the server 130may transmit the first salt and the second salt to the user device. Instep 1225, the first user device 110 may generate a first authenticationstring and a second authentication string. In step 1230, the first userdevice 110 may send (e.g., transmit) a username, the firstauthentication string, and the second authentication string to theserver 130. In step 1235, the server 130 may request apreviously-registered authentication string (e.g., stored authenticationstring) from the database 140. In step 1240, the database 140 mayrespond to the server's request with the previously registeredauthentication string. In step 1245, the server 130 may verify that thefirst authentication string matches the previously-stored authenticationstring. When the authentication strings match, the server 130 maytransmit a request to database 140 to update the salt and authenticationstring associated with the username in step 1250.

One or more aspects discussed herein may be embodied in computer-usableor readable data and/or computer-executable instructions, such as in oneor more program modules, executed by one or more computers or otherdevices as described herein. Generally, program modules includeroutines, programs, objects, components, data structures, and the like.that perform particular tasks or implement particular abstract datatypes when executed by a processor in a computer or other device. Themodules may be written in a source code programming language that issubsequently compiled for execution, or may be written in a scriptinglanguage such as (but not limited to) HTML or XML. The computerexecutable instructions may be stored on a computer readable medium suchas a hard disk, optical disk, removable storage media, solid-statememory, RAM, and the like. As will be appreciated by one of skill in theart, the functionality of the program modules may be combined ordistributed as desired in various embodiments. In addition, thefunctionality may be embodied in whole or in part in firmware orhardware equivalents such as integrated circuits, field programmablegate arrays (FPGA), and the like. Particular data structures may be usedto more effectively implement one or more aspects discussed herein, andsuch data structures are contemplated within the scope of computerexecutable instructions and computer-usable data described herein.Various aspects discussed herein may be embodied as a method, acomputing device, a system, and/or a computer program product.

By employing the login techniques described herein, the user's passwordmay remain secure on the user device. This reduces the likelihood of amalicious actor obtaining the user's password while the password isin-transit. Additionally, using a derivative of a password forauthentication purposes secures the user's password in case of a breachat the server. This may ensure that other accounts that have the sameusername and password would not be compromised in the event of a breachof the server. Accordingly, the user may not have to take correctiveaction (e.g., update their passwords on other accounts) in response to abreach that occurs at a third-party (e.g., server), thereby improvingthe overall user experience.

Although the present invention has been described in certain specificaspects, many additional modifications and variations would be apparentto those skilled in the art. For example, the techniques described aboveapply to server-client relationships. However, it will be appreciatedthat the techniques described herein may have applicability toserver-to-server communications. Additionally, the techniques describedherein may have applicability to other static information used toauthenticate a user, developer, and/or a program, such as an API key.Moreover, while the techniques have been discussed in a particularsequence, it will be appreciated that any of the various processesdescribed above may be performed in alternative sequences and/or inparallel (on different computing devices) in order to achieve similarresults in a manner that is more appropriate to the requirements of aspecific application. It is therefore to be understood that the presentinvention may be practiced otherwise than specifically described withoutdeparting from the scope and spirit of the present invention. Thus,embodiments of the present invention should be considered in allrespects as illustrative and not restrictive. Accordingly, the scope ofthe invention should be determined not by the embodiments illustrated,but by the appended claims and their equivalents.

What is claimed is:
 1. A method comprising: receiving, by a first devicefrom a second device, a username, a first authentication string, and asecond authentication string, wherein: the first authentication stringcomprises a first hashed representation of the username, a password, anda first salt; and the second authentication string comprises a secondhashed representation of the username, the password, and a second salt;comparing the first authentication string to a previously registeredauthentication string to determine whether the first authenticationstring matches the previously registered authentication string;verifying, based on a determination that the first authentication stringmatches the previously registered authentication string, the usernameand the first authentication string; and replacing, based onverification of the username and the first authentication string, thefirst authentication string with the second authentication string. 2.The method of claim 1, further comprising: sending, to the seconddevice, the first salt and the second salt, wherein the first salt andthe second salt are sent to the second device based on at least one of:a detection of a data breach; or a request to update a passwordassociated with the username.
 3. The method of claim 2, wherein sendingthe first salt and the second salt to the second device comprises:transmitting the first salt and the second salt via a securecommunication channel.
 4. The method of claim 1, wherein receiving theusername, the first authentication string, and the second authenticationstring comprises: receiving the username, the first authenticationstring, and the second authentication string over a secure communicationchannel.
 5. The method of claim 1, wherein replacing the firstauthentication string with the second authentication string comprises:updating a first field in a database entry associated with the usernameto indicate the second authentication string; and updating a secondfield in the database entry by replacing the first salt with the secondsalt.
 6. The method of claim 1, further comprising: sending, to thesecond device and based on the replacing the first authentication stringwith the second authentication string, an acknowledgement thatauthentication information has been updated.
 7. The method of claim 1,further comprising: requesting, based on the verification of theusername and the first authentication string, additional authenticationinformation from the second device; receiving, from the second device,the additional authentication information, wherein the additionalauthentication information comprises at least one of a one-time code ora biometric identifier; and verifying the additional authenticationinformation prior to replacing the first authentication string with thesecond authentication string.
 8. A method comprising: generating, by asecond device, a first authentication string by applying a one-way hashfunction to a first salt, a username, and a password; generating asecond authentication string by applying the one-way hash function to asecond salt, the username, and the password; transmitting, to a firstdevice via a secure communication channel, the username, the firstauthentication string, and the second authentication string; andreceiving, from the first device and based on a determination that thefirst authentication string matches a previously registeredauthentication string, an indication that authentication information hasbeen updated.
 9. The method of claim 8, wherein the first salt and thesecond salt are received from the first device.
 10. The method of claim9, wherein the first salt and the second salt are received in responseto at least one of: a detected breach; or a request to update a passwordassociated with the username.
 11. The method of claim 8, furthercomprising: padding the password prior to generating the firstauthentication string.
 12. The method of claim 11, further comprising:padding the password prior to generating the second authenticationstring.
 13. The method of claim 8, further comprising: receiving, by thesecond device, a request for additional authentication information;transmitting, by the second device to the first device, the additionalauthentication information wherein the additional authenticationinformation comprises at least one of a one-time code or a biometricidentifier; and receiving the indication that authentication informationhas been successfully updated after transmitting the additionalauthentication information.
 14. A system comprising: a servercomprising: one or more first processors; and a first memory storingfirst instructions that, when executed by the one or more firstprocessors, cause the server to: receive, from a user device, ausername, a first authentication string, and a second authenticationstring; compare the first authentication string to a previouslyregistered authentication string associated with the username; verify,based on a determination that the first authentication string matchesthe previously registered authentication string, the username and thefirst authentication string; and replace the first authentication stringwith the second authentication string; and a user device comprising: oneor more second processors; and a second memory storing secondinstructions that, when executed by the one or more second processors,cause the user device to: generate the first authentication string byapplying a one-way hash function to a first salt, the username, and apassword; generate the second authentication string by applying theone-way hash function to a second salt, the username, and the password;transmit the username, the first authentication string, and the secondauthentication string; and receive an indication that authenticationinformation has been updated.
 15. The system of claim 14, wherein thefirst instructions, when executed by the one or more first processors,cause the server to: generate the first salt and the second salt using apseudorandom number generator; and transmit, to the user device, thefirst salt and the second salt.
 16. The system of claim 15, wherein thesecond instructions, when executed by the one or more first processors,cause the user device to: receive the first salt and the second salt.17. The system of claim 15, wherein the first salt and the second saltare received in response to at least one of: a detected breach; or arequest to update a password associated with the username.
 18. Thesystem of claim 14, wherein the first instructions to replace the firstauthentication string with the second authentication string furthercause the server to: update a first field in a database entry associatedwith the username to indicate the second authentication string; andupdate a second field in the database entry by replacing the first saltwith the second salt.
 19. The system of claim 14, wherein the firstinstructions, when executed by the one or more first processors, causethe server to: send, to the user device, an acknowledgement thatauthentication information has been updated.
 20. The system of claim 14,wherein the first authentication string and the second authenticationstring provide access to one or more user accounts hosted on the server.